home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
newsgroups
/
misc.19941031-19941221
/
000247_news@columbia.edu_Wed Nov 23 09:08:34 1994.msg
< prev
next >
Wrap
Internet Message Format
|
2020-01-01
|
3KB
Received: from apakabar.cc.columbia.edu by watsun.cc.columbia.edu with SMTP id AA21451
(5.65c+CU/IDA-1.4.4/HLK for <kermit.misc@watsun.cc.columbia.edu>); Wed, 23 Nov 1994 09:08:34 -0500
Received: by apakabar.cc.columbia.edu id AA05841
(5.65c+CU/IDA-1.4.4/HLK for kermit.misc@watsun); Wed, 23 Nov 1994 09:08:32 -0500
Path: news.columbia.edu!spcuna!solaris.cc.vt.edu!news.mathworks.com!hookup!swrinde!pipex!sunic!news.funet.fi!news.csc.fi!news.helsinki.fi!cc.helsinki.fi!jaakola
From: jaakola@cc.helsinki.fi
Newsgroups: comp.protocols.kermit.misc,alt.winsock
Subject: Re: winsock/MS-Kermit hack possible? (Was: winsock/pkt drv hack...)
Date: 22 Nov 94 22:02:04 EET
Organization: University of Helsinki
Lines: 45
Message-Id: <1994Nov22.220204.1@cc.helsinki.fi>
References: <3a67j8$j39@Mercury.mcs.com> <3anvci$dut@relay.tor.hookup.net> <soren.223.000F87E0@aztec.co.za> <1994Nov21.105430.33454@cc.usu.edu>
Nntp-Posting-Host: hylka.helsinki.fi
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Xref: news.columbia.edu comp.protocols.kermit.misc:1192 alt.winsock:22840
Apparently-To: kermit.misc@watsun.cc.columbia.edu
In article <1994Nov21.105430.33454@cc.usu.edu>, jrd@cc.usu.edu (Joe Doupnik) writes:
> Nice idea but not practical here. There are a great many
> coupling threads (variables, calls) between the high level and comms
> level material in Kermit so that control may be exercised and speed
> retained. And there is much more to comms than serial or the internal
> TCP/IP stack; SET PORT exhibits the list (and some choices transparently
> encompass two or three variations from the same vendor).
> Winsock is for pure Windows programs, not for DOS programs.
> MS-DOS Kermit removes itself from comms channels when done with
> them. Few commercial TCP/IP stacks do so (none that I know of). Were
> winsock guys to get off the pot when done the problem would be smaller.
> So please consider hounding your winsock vendor to go un-TSR upon last
> close and to not be present until an application makes a demand.
> Joe D.
I can use Trumpet Winsock (version 1, beta 6) and MS-Kermit, but not at
the same time, and I can switch back and forth using either one, one at
a time. I use WINPKT+ODITRPKT+ODI drivers.
A guy from New Zealand says that he is able to use Winsock and KA9Q at
the same time without stopping the other one. He is even using the same
IP address for both of them! He uses PKTMUX.
I think that XFS is a hack which allows you to have NFS and Winsock
simultaneously.
Is it possible to use MS-Kermit and Winsock simultaneously with PKTMUX,
and both stacks having the same IP number?
I see the following problems:
Who answers to ICMP echo (ping, that is)? How about other ICMP messages?
How does one avoid using the same port numbers in both stacks? Could Joe
add a client port range parameter to MS-Kermit, and is the same possible
on the Winsock side, so that the two ranges would not overlap? Of
course, for Winsock this would be stack brand dependent. Peter Tattam,
do you hear?
When MS-Kermit 3.14 sends RARP for its own address (the duplicate
check), will the Winsock answer it and thus trigger a false alarm?
Can these problems be circumvented?
--
Juhani Jaakola, jaakola@cc.helsinki.fi